|
1. Selecting testware
In consultation with the future administrator of the system, an inventory is drawn up of which testware is to be made
available to him. The purpose is to render the testware reusable for changes and associated maintenance tests, so that
it will not be necessary to design a completely new test. The final choice of testware to be made available is
made on the basis of a costs/benefits analysis. Subjects in this would be ‘What will it cost to maintain the testware
(storage and updating)’ and ‘What will it cost to make it anew’.
The test products to be delivered are set out in an inventory. This is an overview of the test products to be
preserved. It is important to indicate the way in which the test products were created, in order to facilitate
appropriate future maintenance. Bear in mind here in particular the test design techniques, tools, et cetera that were
used.
|
2. Collecting and refining testware, make it accessible
| The testware to be transferred should be completed and adjusted where necessary. During the last phase of the execution, in
particular, maintenance of the testware is often postponed. Before transfer to the future users can take place, any changes
should be processed. The testware should also be made accessible. This means that it should be stored in such a way that it
is readily available to the future users. That may mean, for example, that the directory structure has to be set up
differently or a particular tool must be used. |
3. Transferring testware
| Finally, the actual transfer of the testware takes place. In accordance with the testware inventory, all the selected parts
are electronically, and sometimes also physically (on paper), transferred to the maintenance department. |
|
